From 692098b151c41b27e5e486a84aa2cfd9dad751c5 Mon Sep 17 00:00:00 2001 From: robertl Date: Thu, 5 Jul 2007 05:07:50 +0000 Subject: [PATCH] Minor doc tweaks in use, preface, build. Try to segment Garmin list into GPX and GPX-not. --- xmldoc/chapters/build.xml | 2 +- xmldoc/chapters/preface.xml | 2 +- xmldoc/chapters/use.xml | 16 ++++++------ xmldoc/formats/garmin.xml | 52 ++++++++++++++++++++++--------------- 4 files changed, 41 insertions(+), 31 deletions(-) diff --git a/xmldoc/chapters/build.xml b/xmldoc/chapters/build.xml index 67284051c..377f8f9dc 100644 --- a/xmldoc/chapters/build.xml +++ b/xmldoc/chapters/build.xml @@ -37,7 +37,7 @@ need to 'apt-get install libusb-dev'. ./configure --help -lists all the supported options, but additionally we have: +lists all the supported options, but additionally we have: Excludes the shapefile support. diff --git a/xmldoc/chapters/preface.xml b/xmldoc/chapters/preface.xml index a839143e6..4ce0e356a 100644 --- a/xmldoc/chapters/preface.xml +++ b/xmldoc/chapters/preface.xml @@ -1,7 +1,7 @@ Introduction
- The Problem: Too many incompatible formats + The Problem: Too many incompatible GPS file formats There are simply too many gratuitously different file formats to hold waypoint, track, and route information in various programs used by computers and GPS receivers. diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml index 42bb08988..167f475b3 100644 --- a/xmldoc/chapters/use.xml +++ b/xmldoc/chapters/use.xml @@ -54,15 +54,15 @@ name of a file to be read or written. it from, what you're writing, and what to write it to. For example: gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx - tells it to read the file "/tmp/geocaching.loc" in geocaching.com - format and create a new file in GPX format. + tells it to read the file /tmp/geocaching.loc in geocaching.com + format and create a new file /tmp/geocaching.gpx in GPX format. It's important to note that the names have nothign to do with the formats actually used. This command will read from a Magellan unit attached to the first serial port on a Linux system (device names will - vary on other OSes) and write them as a geocaching loc file. - The second command does the same on Microsoft Windows. + vary on other OSes) and write them as a geocaching loc file. gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc + This second command does the same on Microsoft Windows. gpsbabel -i magellan -f com1 -o geo -F mag.loc - Optionally, you may specify "-s" in any command line. This + Optionally, you may specify -s in any command line. This causes the program to ignore any "short" names that may be present in the source data format and synthesize one from the long name. This is particularly useful if you're writing to @@ -81,7 +81,7 @@ name of a file to be read or written. Many of the available format options in GPSBabel can themselves take options. While we try to make all the formats do the most - sensible thing possible without any extra options, this allows + sensible thing possible without any extra options; this allows great power and flexibility in the operation of the program. @@ -136,7 +136,7 @@ merged data to multiple destinations. of supported character sets with "gpsbabel -l". To change the character set on both sides you should do this: gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar - Note, that some formats has a fixed character set and ignore this option. + Note, that some formats have a fixed character set and ignore this option. Route and Track Modes @@ -162,7 +162,7 @@ merged data to multiple destinations. may not really be the route you had in mind. Tracks and routes will sometimes be converted to a - list of waypoints when necessary, f.i. when writing into one + list of waypoints when necessary, One example is when writing into one of the CSV formats. The inverse operation is not supported right now, so reading the converted track back from CSV will always result in a list of waypoints, not the original track. diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml index 3f30e6a93..3a0c74de3 100644 --- a/xmldoc/formats/garmin.xml +++ b/xmldoc/formats/garmin.xml @@ -50,21 +50,6 @@ GPSMAP 76Cx GPSMAP 96 GPSMAP 96C -Nuvi 300This unit uses GPX format, not Garmin protocol. Therefore one should communicate with it by reading and writing GPX files instead of using this format. Members of this class of products do not support realtime positioning protocol. -Nuvi 200 -Nuvi 200W -Nuvi 250 -Nuvi 250W -Nuvi 270 -Nuvi 310 -Nuvi 350 -Nuvi 370 -Nuvi 600 -Nuvi 650 -Nuvi 650FM -Nuvi 660 -Nuvi 670 -Nuvi 680 Quest Quest II Rhino 520 @@ -83,15 +68,9 @@ StreetPilot c320 StreetPilot c330 StreetPilot c340 -StreetPilot c510 -StreetPilot c530 -StreetPilot c550 -StreetPilot c580 StreetPilot i2 StreetPilot i3 StreetPilot i5 -Zumo 450 -Zumo 550 the following Bluetooth Garmin products: @@ -100,6 +79,7 @@ + and most serial Garmin GPS receivers including: eMap @@ -131,6 +111,36 @@ + +The following Garmin GPS receivers are supported, but they do not +support Garmin communication protocol and don't work with the + option. To use these receivers, read or write +GPX files from the mass storage device as mounted on your computer. + +Nuvi 200 +Nuvi 200W +Nuvi 250 +Nuvi 250W +Nuvi 270 +Nuvi 300This unit uses GPX format, not Garmin protocol. Therefore one should communicate with it by reading and writing GPX files instead of using this format. Members of this class of products do not support realtime positioning protocol. +Nuvi 310 +Nuvi 350 +Nuvi 370 +Nuvi 600 +Nuvi 650 +Nuvi 650FM +Nuvi 660 +Nuvi 670 +Nuvi 680 +StreetPilot c510 +StreetPilot c530 +StreetPilot c550 +StreetPilot c580 +Zumo 450 +Zumo 550 + + + None of the GPSBabel developers has access to every model on that list, but we've received reports of success and/or have reasonable -- 2.30.2